FILESOFT SKIPPED RECURRING TASKS 0.1.0
Editable single-user teaching file for FileMaker Pro

Keep a recurring occurrence when work is skipped. Save a reason, generate the
range again without recreating it, then restore the same task when appropriate.
This is an independent teaching example, not an Asset Care product update.

GET STARTED
Open Filesoft Skipped Recurring Tasks_0.1.0.fmp12 in FileMaker Pro on macOS.
Use Load examples if needed. It adds missing examples; it does not reset tasks.
This download preserves the owner's walkthrough copy, including saved sample
tasks and their history. Read the preview and saved count before making changes.
Select Monthly inspection, set First occurrence 0 and Count 6, then Preview range.
Create missing creates only missing keys. Click Review beside MAINT-A:1.
If already Skipped, Restore it first to practice a new skip. Enter a reason such
as Equipment unavailable this month, then Skip task. Return to the schedule and
Create missing again: existing tasks, including Skipped tasks, remain unchanged.
Increase Count to 8 and preview. Only missing keys will be created; if all eight
already exist, expect zero new tasks. Review February and Restore it to Open.
Keep a closed backup before experimenting. There is no reset/delete button.

RULES TO INSPECT
TaskKey combines ScheduleID and Occurrence. Status does not change that identity.
ScheduledDate and AdjustedDeadline remain unchanged by Skip and Restore.
Skip requires a nonblank reason of up to 240 characters after whitespace cleanup.
Cancel discards the unsaved draft only. Restore clears the current skip reason;
the earlier reason remains in status history. Repeating the same status action
does not append a duplicate history entry. The detail shows the last three actions.
History is editable teaching data, not a tamper-resistant audit trail.
First occurrence: integer 0-1200. Count: integer 1-12. Occurrence 0 is the anchor.
Five fixed examples: Monthly inspection, Same deadline, Leap-day inspection,
Rollback practice and Date boundary. Test rejected batch belongs to Rollback
practice and requires a range with missing tasks. It should save no new tasks.
Inspect Schedules and Tasks, and the UI/Controller scripts under App > Recurring
tasks in Script Workspace. The generator checks keys regardless of status.

COMPATIBILITY AND TEST SCOPE
Designed for FileMaker Pro 19.6.1 or later; transaction steps require 19.6.1.
FileMaker Pro is not included. Native checks used FileMaker Pro 26.0.3 on macOS
in an isolated copy: skip/restore, reason validation, repeated actions, cancelled
drafts, regeneration, range extension, separate schedules, rejected batches and
normal close/reopen persistence. Owner screenshots illustrate the main workflow.
Older versions, Windows, Go, WebDirect, hosting, concurrent sessions and crash
recovery have not been tested. Shorter windows may need vertical scrolling.
Fixed schedules only: no completion workflow, reminders, automatic background
generation, deletion or schedule revisions. No analytics in the teaching file.
